home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19980424-19980901
/
000239_news@newsmaster….columbia.edu _Tue Jun 30 07:32:57 1998.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id HAA27441
for <kermit.misc@watsun.cc.columbia.edu>; Tue, 30 Jun 1998 07:32:57 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id HAA09933
for kermit.misc@watsun; Tue, 30 Jun 1998 07:32:56 -0400 (EDT)
Path: news.columbia.edu!panix!howland.erols.net!nntp.abs.net!chippy.visi.com!news-out.visi.com!ptah.visi.com!not-for-mail
From: "Teo" <teo@itbctech.com>
Newsgroups: comp.protocols.kermit.misc
Subject: script not working on 95
Lines: 38
X-Newsreader: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Message-ID: <x14m1.2195$P8.7988685@ptah.visi.com>
Date: Tue, 30 Jun 1998 11:32:45 GMT
NNTP-Posting-Host: 209.98.4.62
NNTP-Posting-Date: Tue, 30 Jun 1998 06:32:45 CDT
Xref: news.columbia.edu comp.protocols.kermit.misc:8935
I have a script that dies on all new Windows95 machines. I apologize for
the long post but more info might be of help. Here are the particulars.
Kermit for DOS (misc versions) works fine on 386 and 486 and P60,P90s.
K-95 version 1.10 thru 1.15 works fine on NT workstations - P200+,and
PII-233s
We are using Kermit for DG/UX version 5 (but the process dies before
connecting)
On all P-100 and above in windows95, DOS Kermit and K-95 v1.15 the following
happens in the script:
1. we use "OUTPUT AT&Fxxxxxx" (xx is misc RTS info, etc needed for the
transfers) to initialize the modem, then "INPUT 15 OK" to wait for the OK
prompt. We never get the ok. In our logs that are trapped it appears as if
the output is not sent.
2. If step 1 occasionally works (twice) then the next step where we output
the number to dial ends up not getting to the modems.
If we do this manually with a STOP command to get out - it works fine. We
connect and process the information. We have tried different PCs and both
versions of Windows95 A and B. We have put in additional PAUSE statements
to slow the script down and that still doesn't fix the problems. We have
also put multiple output commands, one after the other but it doesn't get to
the Modem. We are defining the modems as TAPI but have tried directly to
the COM ports also.
Any ideas are greatly appreciated. This is a major piece of my customers
solution and the users are out in BFE and not intelligent enough to manually
enter the output command and then go back to the script.
Thanks in advance.
Teo leonard
iT Business Consulting
teo@itbctech.com